Auto-Generated Summary

> Provide an extensive summary of the agreements by topic. No need to mention CRs.

Summary of Agreements by Topic

UE Complexity Reduction

1. Peak Data Rate Target:
• The peak rate target for Rel-18 eRedCap UEs is set at 10 Mbps, regardless of optional features supported.
• For peak data rate reduction:
• With UE BB bandwidth reduction: vLayers·Qm·f = 3.2.
• Without UE BB bandwidth reduction: vLayers·Qm·f = 0.75 (assuming 20 MHz bandwidth in the 38.306 peak rate expression).
2. Bandwidth Reduction:
• Maximum PRBs:
• For PUSCH: 25 PRBs for 15 kHz SCS and 12 PRBs for 30 kHz SCS.
• For PDSCH (unicast and broadcast): Same limits as PUSCH.
• Scheduling of Channels:
• SIB1, OSI, paging, and RAR PDSCH can be scheduled larger than 5 MHz and up to the maximum PRBs allowed.
• Multicast/Broadcast:
• For multicast MBS specified in Rel-17, the number of PRBs scheduled in DCI is not larger than 25 PRBs for 15 kHz SCS or 12 PRBs for 30 kHz SCS.
3. Simultaneous Reception:
• For FDMed unicast and multicast/broadcast PDSCH:
• The UE can decode two PDSCHs partially or fully overlapping in time in non-overlapping PRBs if the total PRBs allocated are within the maximum limits.
• If the total PRBs exceed the maximum, the UE may skip decoding one of the PDSCHs.
4. Relaxed Timelines:
• Timeline relaxations apply for:
• Msg2-Msg3: 1 slot for Msg2 PDSCH larger than the maximum PRBs.
• 2-step RACH:
• Between reception of fallbackRAR/successRAR and Msg3 transmission.
• Between reception of MsgB PDSCH and PRACH transmission.
5. Early Indication:
• Rel-18 eRedCap UEs share MsgA PRACH configured for Rel-17 RedCap UEs if performing 2-step RACH.
• Additional early indication in MsgA PRACH is not supported.

Multicast/Broadcast Handling

1. Simultaneous Reception:
• An eRedCap UE can decode simultaneous MBS multicast and unicast PDSCHs if the total PRBs do not exceed the maximum limits.
• For simultaneous MBS broadcast and unicast when PRBs exceed the maximum, further discussion is required.
2. MCCH and PBCH:
• The UE is expected to decode PDSCH scheduled with MCCH-RNTI and PBCH in PCell that partially or fully overlap in time in non-overlapping PRBs.

Random Access

1. Msg3 PUSCH:
• A UE does not expect to transmit a PUSCH over a bandwidth larger than the maximum PRBs per hop in a slot for:
• RAR UL grant.
• DCI scrambled by TC-RNTI.
• Type-2 random access procedure.
2. FallbackRAR and MsgB:
• For MsgB PDSCH scheduled by MSGB-RNTI:
• If the UE does not correctly receive the transport block or RAPID, it shall be ready to transmit PRACH within specified timelines.

Optional Features

1. Rel-18 eRedCap UEs:
• Optional features include:
• 2 Rx branches with DL MIMO.
• DL 256QAM.

Specification Clarifications

1. Handling of Multiple PDSCHs:
• During P-RNTI triggered SI acquisition, if the total PRBs exceed the maximum, the UE may skip decoding PDSCH scheduled with C-RNTI/MCS-C-RNTI/CS-RNTI.
2. FG 48-2 UEs:
• RAR PDSCH timeline relaxation does not apply to FG 48-2 UEs for CFRA.
3. Specification Updates:
• Clarifications on "A UE that has not indicated FG 48-2" and "A UE that indicated FG 48-2" are under discussion.

Higher Layer Signaling

1. Peak Rate Parameters:
• Rel-18 eRedCap UEs signal peak data rate-related parameters corresponding to vLayers, Qm, and f.
• No new values for these parameters will be introduced.

LS to RAN2

1. Inform RAN2:
• Agreements on MsgA PRACH sharing and peak rate-related capability parameters were communicated to RAN2.

This summary captures the key agreements and decisions made across sessions regarding Rel-18 eRedCap UE complexity reduction and related topics.